Dive into a lower layer and you suddenly fall into a higher layer.
dmikurube I've always been someone who dives into the lower layer of software, but when I'm diving down, I suddenly drop down into the layer above the software (people I've always been a lower layer diver of software, but when I'm diving down, I'll suddenly drop into the layer above the software (person to person or politics), like if I'm moving down the screen, I'll come out of the top. The minuscule and the maxuscule are connected, and when you get to a certain point, it suddenly reverses. dmikurube In general, the software infrastructure of the lower layers is dependent on the upper layers because it takes on the common tasks of the upper layers. This creates dependence on continuity and compatibility, as changes in the lower layers may unintentionally cause catastrophic effects on the upper layers. As a result, it becomes difficult to change the lower layers. creat (2) still has no e dmikurube It's just fun to dive in and play. When you become responsible for "maintaining" the lower tier, you will encounter situations where you have to make changes to the lower tier, and you will have to face these problems. You have to face the real demands of the people in the upper layer, or negotiate and get them to give up. The layers of the story jump off the page. dmikurube When designing the lower layers, if you don't imagine how things will look in the future, you could be left with decade-long disasters if you are not careful. However, software engineering with such a long time horizon has not been done systematically, so it tends to be a craftsman's art. ---
This page is auto-translated from /nishio/低レイヤーに潜ると、急に上のレイヤーに落ちてくる using DeepL. If you looks something interesting but the auto-translated English is not good enough to understand it, feel free to let me know at @nishio_en. I'm very happy to spread my thought to non-Japanese readers.